=== Pavo Core ===

Contributors: pavothemes
Donate link: https://pavothemes.com
Tags: elementor, theme builder, megamenu, dynamic tags, widgets
Tested up to: 6.6
Stable tag: 2.0.3
License: GPLv3
License URI: https://www.gnu.org/licenses/gpl-3.0.html

== Description ==

Pavo Core is the foundation plugin for all PavoThemes WordPress themes.

It extends Elementor with powerful Theme Builder capabilities, Mega Menu, Dynamic Tags, Custom CSS, Motion Effects, and a collection of useful widgets, allowing you to build fully customized websites without modifying your theme.

Built with a modern PSR-4 architecture, Pavo Core is optimized for performance, backward compatibility, and long-term maintainability.

= Features =

* Theme Builder (Header, Footer, Archive, Single, Custom Block, Mega Menu)
* Advanced Display Conditions similar to Elementor Pro
* Mega Menu Builder powered by Elementor
* Dynamic Tags for Elementor
* Motion Effects and Sticky Elements
* Custom CSS support
* Additional Elementor widgets
* WPML compatible
* Modern PSR-4 architecture
* Reorganized, maintainable asset build pipeline
* Backward compatibility with previous Pavo Core releases

Documentation:
https://docs.pavothemes.com/

Support:
https://pavothemes.ticksy.com/

== Installation ==

1. Upload the plugin to the `/wp-content/plugins/` directory, or install it from the WordPress Plugins screen.
2. Activate **Pavo Core** from the **Plugins** page.
3. Make sure Elementor is installed and activated.
4. Open **Pavo Core → Theme Builder** to start creating templates such as Header, Footer, Archive, Single, or Mega Menu.

== Frequently Asked Questions ==

= Does Pavo Core require Elementor? =

Yes. Elementor is required to use the Theme Builder, widgets, Dynamic Tags, Mega Menu, and other builder features.

= Is Elementor Pro required? =

No. Pavo Core works with the free version of Elementor. When Elementor Pro is installed, compatible features are automatically detected to avoid conflicts.

= Is WPML supported? =

Yes. Theme Builder display conditions fully support WPML and correctly resolve translated pages, posts, products, and taxonomy terms.

= Will updating from older versions break my existing templates? =

No. Pavo Core preserves backward compatibility with previous releases. Existing Theme Builder templates, display conditions, and legacy configuration continue to work after upgrading.

== Upgrade Notice ==

= 2.0.1 =

This release fixes two Theme Builder display-condition backward-compatibility issues, adds WPML support for display conditions, and reorganizes the asset build pipeline — all while preserving existing site behavior. Note: if a child theme or customization links directly to a file under assets/build/ instead of using the plugin's registered script/style handle, that direct link will break, since assets/build/ no longer exists.

== Changelog ==

= 2.0.24 =

* Fixed: Menu widget's CSS/JS loaded too late (in the footer instead of <head>) when the widget lives inside a Theme Builder Header/Footer template — caused a real flash-of-unstyled-menu on first paint. Now preloaded in <head> whenever a Header/Footer template is active.

* Improved: Menu widget mobile off-canvas panel — optional title/header, item dividers, and active-item highlighting.
* Improved: Menu widget Vertical layout — submenus and mega panels now fly out beside the item on hover, with Auto/Left/Right positioning and new Menu Wrapper Width / Panel Width controls so the panel opens flush against the menu instead of the full container.
* Improved: Appearance → Menus Mega Menu UI — a persistent [Mega] indicator on top-level items (shows enabled state at a glance, no more hover-only button), a separate Menu Item Settings panel for Icon/Badge available on every item (previously only reachable through the Mega Menu modal on top-level items), and clearer labels/width units on the Mega Menu Settings modal. Existing Icon/Badge/Mega data is read and saved exactly as before.

= 2.0.0 =

* New: WPML support for Theme Builder display conditions with automatic translated object resolution.
* Fixed: Theme Builder User Roles conditions now work correctly while preserving existing site behavior (previously saved but silently ignored).
* Fixed: Unknown legacy display conditions (custom taxonomies, theme-added rules, etc.) are no longer discarded during evaluation.
* Improved: Legacy display conditions continue to work without requiring data migration.
* Improved: Asset build pipeline reorganized — editable source now under `assets/src/`, generated assets in `assets/css/` and `assets/js/` instead of `assets/build/`. Every enqueued script/style handle and dependency is unchanged; a direct link to a file under the old `assets/build/` path will break.

= 1.0.0 =

* Initial release.
